-
Notifications
You must be signed in to change notification settings - Fork 0
Add workspace creation protocol. #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
c5f88f2
to
0706bb1
Compare
addressed review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
guess further feedback would need actually trying to impl this
dd96548
to
0b76622
Compare
Given further thought, this won't be very useful without considerably more data, and the most flexible solution that sets expectations properly is to just not do it. Not exposing anything makes client UI harder to handle but should also force clients not to make incorrect assumptions, and instead use targets to probe for capabilities where they plan to create a workspace. |
0b76622
to
fc7609f
Compare
This protocol allows workspaces to be created outside of ext-workspace's create-by-name strategy.
Many compositors create workspaces dynamically based on content or focus. This attempts to encompass all common strategies I'm aware of, and leaves the door open for compositor specific workspace creation methods to use most of the protocol.
This is commonly used by bars and workspace switchers.